Node Group Waste View

Cluster

The cluster name containing the node group.

By default this table is sorted Cluster then Node Groups, in alphabetic order.

Node Group

The node group name.

For nodes that do not belong to a node group, node group value will be <cluster-name>-default”.

CPU Capacity - Allocatable (Cores)

This is the average number of cores available for your container workloads.

This value is determined from the number of hours each node was running in the last 7 days and using that value to calculate how many cores are available on average.

Average CPU Utilization (%)

The average CPU utilization, during the past 7 days of history.

This value is weighted by the number of hours that each node in the group ran. The CPU utilization is multiplied by the number of running hours for the node before calculating the average.

Surplus CPUs (Cores)

The number of surplus cores currently provisioned.

The surplus number of CPU cores for the node group, based on how many CPUs are utilized as compared to the total allocatable number of CPUs.

If the node type is not one “Compute Optimized", “General Purpose”, or “Memory Optimized” then this value cannot be determined and is indicated as a dash (-).

Memory Capacity - Allocatable (GB)

This is the average amount of memory available for your container workloads.

This value is determined from the number of hours each node was running in the last 7 days and using that value to calculate how much memory is available on average.

Average Memory Utilization (%)

The average memory utilization during the past 7 days of history.

This value is weighted by the number of hours that each node in the group ran. The memory utilization is multiplied by the number of running hours for the node before calculating the average.

Surplus Memory (GB)

The amount of surplus memory currently provisioned.

The surplus memory of the node group based on how much memory is utilized as compared to the total allocatable amount of memory.

If the node type is not one “Compute Optimized", “General Purpose”, or “Memory Optimized” then this value cannot be determined and is indicated as a dash (-).

Primary Constraint

Indicates the reason that more containers cannot be added to this node group. The following values are evaluated and whichever has the largest value is identified as the primary constraint:

• CPU Request—Based on the value of CPU Request (Capacity %)
• CPU Utilization—Based on the value of Average CPU Utilization (%)
• Memory Request—Based on the value of Memory Request (Capacity %)
• Memory Utilization—Based on the value of Average Memory Utilization (%)

Current Node Family

This is the current value. The node is categorized as one of “Compute Optimized", “General Purpose”, or “Memory Optimized”.

Fully Optimized Node Family

Use this value to determine if your nodes are utilized as efficiently as possible. Both CPU and memory utilization are used to determine this ratio. Additionally, the following factors are taken into consideration when calculating the value.

• Kubernetes Headroom-This is the CPU and memory allocation required by Kubernetes to manage the containers.
• Node Type-The node is categorized as one of “Compute Optimized", “General Purpose”, or “Memory Optimized”.

If the node type is not one “Compute Optimized", “General Purpose”, or “Memory Optimized” then this value cannot be determined and is indicated as a dash (-).

Estimated Waste ($/Month)

This is the estimated wasted spend per month. If the value is negative your infrastructure may be under-provisioned.

Calculated as: Fully Optimized Estimated Cost - Current Estimated Cost

If the node type is not one “Compute Optimized", “General Purpose”, or “Memory Optimized” then this value cannot be determined and is indicated as a dash (-).

Total

The totals at the bottom of the table indicate the total for each column, for all pages, if you have a multi-page report.

Vertical scroll bars may be displayed to scroll through the entire list, so lower rows may be momentarily hidden behind the row of Totals.